ci: give every job a timeout instead of the 6h default - #71
Merged
Merged
Conversation
Every job in this repo ran with the GitHub default of 360 minutes, so a job that wedges on a network stall burns six hours of runner time and needs a human to notice and cancel it. That happened today on the synapse repo, where a package build stalled fetching from a degraded Ubuntu mirror. Caps are a backstop, not a performance budget: each sits well above the slowest successful run observed in recent history (build 2m, docker-build 2m, prepare/merge under a minute).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every job in this repo ran with the GitHub default of 360 minutes, so a job
that wedges on a network stall burns six hours of runner time and needs a
human to notice and cancel it. That happened today on the synapse repo, where
a package build stalled fetching from a degraded Ubuntu mirror.
Caps are a backstop, not a performance budget: each sits well above the
slowest successful run observed in recent history (build 2m, docker-build 2m,
prepare/merge under a minute).
build.yamlrelease.yamlrelease.yamlrelease.yamlPart of a sweep across the three repos.